Skip to content

[eng-3646] migrate off Vercel (Next.js → Vite)#86

Open
dnehl wants to merge 1 commit into
mainfrom
eng-3646-migrate-fireblocks-dapp-off-vercel
Open

[eng-3646] migrate off Vercel (Next.js → Vite)#86
dnehl wants to merge 1 commit into
mainfrom
eng-3646-migrate-fireblocks-dapp-off-vercel

Conversation

@dnehl

@dnehl dnehl commented Jun 25, 2026

Copy link
Copy Markdown

Migrate the standalone Fireblocks dApp from Next.js/Vercel to a Vite SPA
deployed on AWS Amplify, mirroring the admin-dashboard setup.

  • Replace Next.js with Vite + @vitejs/plugin-react and the Vanilla Extract Vite plugin; add index.html + src/main.tsx entry point
  • Merge layout.tsx/page.tsx into src/app/app.tsx; move layoutContainer off and set html/body/#app height in global styles
  • Drop next/dynamic (direct re-exports), swap next/image for , remove "use client" directives, and use static asset URLs (firebaseLogo, icon.png moved to public/)
  • Switch env access to import.meta.env.VITE_API_KEY (+ vite-env.d.ts)
  • Add mise.toml + mise.lock (node 24.15.0, pnpm 10.33.2) and regenerate the pnpm lockfile; set tsconfig moduleResolution to bundler
  • Update biome ignores (.next → dist) and pin schema to 2.3.11
  • Add amplify.yml and .github/workflows/ci.yml (mise + lint + build)

@dnehl
feat: migrate off Vercel (Next.js → Vite)
db63593 
  Migrate the standalone Fireblocks dApp from Next.js/Vercel to a Vite SPA
  deployed on AWS Amplify, mirroring the admin-dashboard setup.

  - Replace Next.js with Vite + @vitejs/plugin-react and the Vanilla Extract
    Vite plugin; add index.html + src/main.tsx entry point
  - Merge layout.tsx/page.tsx into src/app/app.tsx; move layoutContainer off
    <body> and set html/body/#app height in global styles
  - Drop next/dynamic (direct re-exports), swap next/image for <img>, remove
    "use client" directives, and use static asset URLs (firebaseLogo, icon.png
    moved to public/)
  - Switch env access to import.meta.env.VITE_API_KEY (+ vite-env.d.ts)
  - Add mise.toml + mise.lock (node 24.15.0, pnpm 10.33.2) and regenerate the
    pnpm lockfile; set tsconfig moduleResolution to bundler
  - Update biome ignores (.next → dist) and pin schema to 2.3.11
  - Add amplify.yml and .github/workflows/ci.yml (mise + lint + build)
@socket-security

socket-security Bot commented Jun 25, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedvite@​8.1.0991008298100
Added@​vitejs/​plugin-react@​6.0.310010010094100
Added@​vanilla-extract/​vite-plugin@​5.2.31001009996100

View full report

@socket-security

socket-security Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/vite@8.1.0 → npm/@emnapi/runtime@1.11.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@dnehl dnehl requested review from Philippoes and petar-omni and removed request for petar-omni June 25, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Philippoes Philippoes Awaiting requested review from Philippoes

At least 2 approving reviews are required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@dnehl